Technique for conserving software application resources

ABSTRACT

Systems and methods of adjusting allocated hardware resources to support a running software application are disclosed. A system includes adjustment logic to adjust an allocation of a first hardware resource to support a running software application. Measurement logic measures at least one hardware resource metric associated with the first hardware resource. Service level logic calculates an application service level based on the measured at least one hardware resource metric. When the first application service level satisfies a threshold application service level, the allocation of the first hardware resource is iteratively reduced to reach a reduced allocation level where the application service level does not satisfy the threshold application service level. In response thereto, the allocation of the first hardware resource is increased by an increment, such that the application service level again satisfies the threshold application service level.

BACKGROUND

It is often difficult to estimate a specific amount of hardwareresources that should be allocated to a software application to meet adesired application service level. The problem exists both at the timeof software installation and after the software has been in use for aperiod of time. As a result of this difficulty, hardware resources areoften over-allocated, leading to higher hardware and management costsand higher energy consumption.

An individual software application (e.g., a database application) may bedeployed to a dedicated hardware resource (e.g., a computer). Over time,it may become apparent that costs are higher than necessary due to anover-allocation of hardware resources. It may be advantageous tore-install multiple software applications together on a reduced numberof computers to share resources (e.g., computer server consolidation).In practice, this is often difficult because the installed softwareapplications may have access to all of the available hardware resources(e.g., when hardware resources are dedicated to an individual softwareapplication). When the software applications are re-installed togetheron a shared computer, it may be difficult to properly allocate hardwareresources of the shared computer between the different softwareapplications.

Prediction algorithms may be used to allocate a minimum necessary amountof hardware for a software application. However, due to the complexityof many software application workloads and their relationships tohardware resources, these prediction algorithms may be unreliable.Alternatively, a software application may provide a capability torelease memory available to itself to reduce resource usage. However,the process of releasing memory may result in an undesired change ofapplication service level as a result of an increase in the usage ofother hardware resources available to the software application. Forexample, releasing memory may increase permanent storage input/output(I/O), resulting in a poor quality application service level when thesoftware application accesses the slower permanent storage devices.

SUMMARY

The present disclosure relates to an automated adaptive technique forreducing hardware resources allocated to support a running softwareapplication while supporting a desired application service level. Thepresent disclosure takes advantage of adaptive runtime adjustment ofhardware resources. As the hardware resources allocated to support therunning software application are reduced, an application service leveleventually fails to satisfy a threshold associated with the desiredapplication service level. When the threshold is reached, the process ofadaptive runtime adjustment is complete, leaving the softwareapplication with a level of hardware resources needed to meet thedesired application service level. Since the reduction in hardwareresources is applied dynamically in an execution environment, thetechnique is a more reliable and more accurate method of adjustinghardware resource allocations to a software application than certainconventional prediction-based techniques.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram that illustrates an embodiment of a system toadjust hardware resources allocated to support a software applicationand to measure an application service level;

FIG. 2 is a flow diagram that illustrates an embodiment of a method ofadjusting hardware resources allocated to support a softwareapplication;

FIG. 3 is a flow diagram that illustrates another embodiment of a methodof adjusting hardware resources allocated to support a softwareapplication;

FIG. 4 is a flow diagram that illustrates another embodiment of a methodof adjusting hardware resources allocated to support a softwareapplication; and

FIG. 5 is a block diagram depicting a general purpose computing systemoperable to enable computer-implemented methods as illustrated in FIGS.1-4.

DETAILED DESCRIPTION

The present disclosure presents an automated adaptive technique forreducing hardware resources allocated to support a running softwareapplication while supporting a desired application service level. Thepresent disclosure relates to systems and methods of adaptive runtimeadjustment of hardware resources supporting a running softwareapplication. One or more hardware resources supporting the runningsoftware application may be targeted for reduced allocation. Appropriatereduced allocations of the one or more hardware resources may bedetermined. By determing the appropriate reduced allocations and byre-allocating hardware resources accordingly, hardware and managementcosts and energy consumption may be reduced.

In a particular embodiment, a system is disclosed that includesadjustment logic to adjust an allocation of a first hardware resource tosupport a running software application. The system also includesmeasurement logic to measure at least one hardware resource metricassociated with use of the first hardware resource by the softwareapplication. Service level logic calculates an application service levelbased on the measured at least one hardware resource metric. When thefirst application service level satisfies a threshold applicationservice level, the allocation of the first hardware resource isiteratively reduced to reach a reduced allocation level where theapplication service level does not satisfy the threshold applicationservice level. In response thereto, the allocation of the first hardwareresource is increased by an increment, such that the application servicelevel again satisfies the threshold application service level.

In another particular embodiment, a method includes identifying a firsthardware resource of one or more hardware resources. The one or morehardware resources support execution of a running software application.At least one hardware resource metric associated with use of the firsthardware resource by the running software application is measured. Anapplication service level is calculated based on the measured at leastone hardware resource metric associated with the first hardwareresource. The calculated application service level is compared to athreshold application service level. When the calculated applicationservice level satisfies the threshold application service level, anallocation of the first hardware resource is reduced until thecalculated application service level does not satisfy the thresholdapplication service level. When the calculated application service leveldoes not satisfy the threshold application service level, the allocationof the first hardware resource is increased such that the calculatedapplication service level satisfies the threshold application servicelevel.

In another particular embodiment, a computer readable storage medium isdisclosed. The computer readable storage medium includes instructions,that when executed by a processor, cause the processor to identify afirst hardware resource of one or more hardware resources. The one ormore hardware resources support execution of a running softwareapplication. At least one hardware resource metric associated with thefirst hardware resource is measured. An application service level basedon the measured at least one hardware resource metric associated withthe first hardware resource is calculated and compared to a thresholdapplication service level. When the calculated application service levelsatisfies the threshold application service level, the allocation of thefirst hardware resource is reduced until the calculated applicationservice level does not satisfy the threshold application service level.Upon detecting that the calculated application service level does notsatisfy the threshold application service level, the allocation of thefirst hardware resource is automatically increased such that thecalculated application service level satisfies the threshold applicationservice level.

Referring to FIG. 1, a system is disclosed that includes a computersystem 102 that includes one or more software applications (e.g.,software application 104) and one or more hardware resources 106. Asystem analyzer 108 includes adjustment logic 110, measurement logic112, service level logic 114, and one or more hardware resourceadjustment inputs 116. The adjustment logic 110 adjusts an allocation118 of a particular hardware resource of the computer system 102 tosupport a running software application (e.g., the software application104). The allocation 118 of the particular hardware resource representsa fraction of the particular hardware resource that is made available tosupport the running software application. The measurement logic 112measures hardware resource metrics 120 of the computer system 102.

The system uses a specific set of initial information (e.g., one or morehardware resource adjustment inputs 116) and subsequently applies ahardware resource adjustment method for reducing hardware resourcesallocated to support the running software application while measuring animpact on an application service level of the running softwareapplication. In the embodiment shown in FIG. 1, the one or more hardwareresource adjustment inputs 116 include identified hardware resources130, resource application programming interfaces (APIs) 132, resourcemetrics 134, target (e.g., threshold) values 136, analysis intervals138, reduction seeds 140, polling intervals 142, and adjustment orders144. One or more of these hardware resource adjustment inputs 116 may beincluded in the hardware resource adjustment method.

The identified hardware resources 130 represent particular hardwareresources that are targeted for reduction (e.g., an amount of memory ora number of available processors). The identified hardware resources 130represent one or more hardware resources supporting the running softwareapplication. The resource APIs 132 identify one or more software APIsused to adjust allocations of each of the identified hardware resources130. Thus, software APIs may be used to adjust an amount (e.g., anallocation) of a particular hardware resource available to support therunning software application. The resource metrics 134 include hardwareresource metrics and the APIs identified as needed to measure anapplication service level of the running software application. Forexample, the identified hardware resource metrics 134 may include aninput/output (I/O) queue length, a transaction latency, or a usage ofallocated processors, among other alternatives. The target values 136identify satisfactory average and peak values for each of the identifiedhardware resource metrics 134 in order to satisfy a desired applicationservice level (e.g., a threshold application service level). Thethreshold application service level may represent a service levelagreement (SLA) with respect to the running software application. Forexample, the SLA may specify an acceptable level of performance of therunning software application. The identified hardware resource metrics134 may be used to determine if the running software applicationperforms at an acceptable level to satisfy the SLA.

The analysis intervals 138 represent time intervals to perform analysisof an impact on the application service level of a change of allocationof a particular hardware resource. A reduction in the allocation of theparticular hardware resource may be reverted at any time during theanalysis interval to an original value if the threshold applicationservice level is not satisfied. Reduction seeds 140 represent changes ofallocation of particular hardware resources at various iterativereduction stages. For example, a first reduction seed may represent afirst reduction of allocation of the particular hardware resource duringa first analysis interval, while a second reduction seed may represent asecond reduction during a second analysis interval. Many periodicmeasurements may be taken at different times during a particularanalysis interval, and polling intervals 142 represent time intervalsseparating the periodic measurements. An adjustment order 144 identifiesan order in which allocations of particular hardware resources areadjusted. For example, an allocation of a first hardware resource 122 tosupport the running software application may be adjusted beforeadjusting allocations of other hardware resources (e.g., a secondhardware resource 124 or a third hardware resource 126).

In the embodiment shown in FIG. 1, the one or more hardware resources106 of the computer system 102 include the first hardware resource 122,the second hardware resource 124, and the third hardware resource 126.In alternative embodiments, the computer system 102 may include anynumber of hardware resources 106. For example, the first hardwareresource 122 may include a logical processing resource that isassociated with at least one physical processing unit (e.g., a centralprocessing unit (CPU)). The second hardware resource 124 may include alogical memory resource that is associated with at least one physicalstorage device. The third hardware resource 126 may include a logicalbandwidth resource associated with at least one device that providesphysical communication bandwidth (e.g., a network resource). Otherhardware resources may also be included in the computer system 102. Forexample, the one or more hardware resources 106 may include bothphysical hardware resources and virtual hardware resources (e.g., cloudcomputing).

In operation, the adjustment logic 110 provides a first allocation 118of a particular hardware resource to support the running softwareapplication 104. For example, the first allocation 118 may be anallocation of the first hardware resource 122 of the one or morehardware resources 106 of the computer system 102. The first hardwareresource 122 supports execution of the software application 104 duringruntime. The first allocation 118 of the first hardware resource 122 iscommunicated from the adjustment logic 110 to the software application104 via one or more software APIs 128. The software APIs 128 may resideon the system analyzer 108, as in FIG. 1, or the software APIs 128 mayreside on the computer system 102 where the software application 104 islocated, or on any other computing system. The first allocation 118 ofthe first hardware resource 122 represents a fraction of the firsthardware resource 108 that is made available to the software application104 (e.g., a percentage of the first hardware resource 108 allocated tothe software application 104). For example, if the first hardwareresource 122 is a processor, the first allocation 118 may be 50% of theavailable processor capacity. As another example, if the first hardwareresource 122 is a storage device, the first allocation 118 may be 30% ofthe storage space available on the storage device. For example, thesoftware application 104 may include a Microsoft SQL Server softwareapplication, and the first allocation 118 to a SQL Server file may be30% of the storage space available.

The software application 104 executes on the computer system 102 and hasaccess to the first allocation 118 of the first hardware resource 122during a first analysis interval (e.g., one of the analysis intervals138 of the hardware resource adjustment inputs 116). The first analysisinterval represents a time interval to perform analysis of an impact ofa change of allocation of a particular hardware resource on anapplication service level of the software application 104. Thus, duringthe first analysis interval, the first allocation 118 of the firsthardware resource 122 that is available to the software application 104remains fixed. This allows measurements to be made for a long enoughperiod of time to obtain accurate hardware resource metrics 120.

The measurement logic 112 measures at least one hardware resource metric120 associated with the first hardware resource 122 during the firstanalysis interval. The measurement logic 112 may measure peak metrics,average metrics, or any other hardware resource metrics. For example,the hardware resource metrics 120 may include a peak input/output (I/O)queue length, a peak transaction latency, a peak usage of allocatedprocessing units, a peak usage of allocated memory, and a peak usage ofallocated storage space. As another example, the hardware resourcemetrics 120 may include an average I/O queue length, an averagetransaction latency, an average usage of allocated processing units, anaverage usage of allocated memory, and an average usage of allocatedstorage space. The measurement logic 112 may periodically measurehardware resource metrics 120 during the first analysis interval. Forexample, many periodic measurements may be taken at different times thatare separated by a time interval (e.g., a polling interval).

The service level logic 114 calculates a first application service levelbased on the hardware resource metrics 120 measured during the firstanalysis interval. The first application service level calculated by theservice level logic 114 is compared to a threshold application servicelevel (e.g., one of the target values 136 of the one of the hardwareresource adjustment inputs 116). The threshold service level identifiessatisfactory average and peak values for the measured hardware resourcemetrics 120. Thus, the threshold application service level represents anacceptable level of performance of the software application 104.

When the first application service level calculated by the service levellogic 114 satisfies the threshold application service level, theadjustment logic 110 provides a second allocation 118 of the firsthardware resource 122 to support the running software application 104.The second allocation 118 is reduced from the initial allocation (e.g.,the first allocation). In a particular embodiment, the second allocation118 is reduced from the initial allocation by a first reduction seed(e.g., one of the reduction seeds 140 of the one or more hardwareresource adjustment inputs 116). For example, the second allocation 118may be 25% lower than the initial allocation. Thus, if the softwareapplication 104 is initially allocated 80% of the first hardwareresource 122, the second allocation 118 may be 60% of the first hardwareresource 122. As an example, if the first hardware resource 122 is aprocessor resource, a percentage of processor capacity (e.g., CPUcapacity) available to the software application 104 may be reduced from80% of available CPU capacity to 60% of available CPU capacity. Thesecond allocation 118 is communicated from the adjustment logic 110 tothe software application 104 via the software APIs 128.

The measurement logic 112 measures the hardware resource metrics 120during a second analysis interval. The second analysis interval may bethe same length of time as the first analysis interval or may be adifferent length of time as compared to the first analysis interval.Further, the second analysis interval may begin immediately after thefirst analysis interval or there may be a delay between the first andsecond analysis intervals. The service level logic 114 calculates asecond application service level based on the hardware resource metrics120 measured during the second analysis interval. When the secondapplication service level calculated by the service level logic 114satisfies the threshold application service level, the adjustment logic110 provides a third allocation 118 of the first hardware resource 122to support the running software application 104. The third allocation118 is reduced from the previous allocation (e.g., the secondallocation). In a particular embodiment, the third allocation 118 isreduced from the previous allocation by a second reduction seed.Reduction seeds may vary between allocation reductions, or the reductionseeds may be the same. Continuing from the previous example, if thesecond reduction seed is the same as the first reduction seed, thepercentage of CPU capacity available to the software application 104 maybe reduced from 60% of available CPU capacity to 45% of available CPUcapacity. Alternatively, if the second reduction seed is not the same asthe first reduction seed, the percentage of available CPU capacity maybe reduced by a different percentage. For example, the percentage of CPUcapacity available to the software application 104 may be reduced from60% of available CPU capacity to 54% of available CPU capacity (e.g., a10% reduction).

The adjustment logic 110 continuously and iteratively provides reducedallocations 118 of the first hardware resource 122 until the servicelevel logic 114 calculates an application service level that does notsatisfy the threshold application service level. When the calculatedapplication service level no longer satisfies the threshold applicationservice level, the allocation of the first hardware resource 122 tosupport the running software application 104 is determined to beinadequate. When the allocation is inadequate, the last allocationadjustment may be reverted such that an adequate allocation of theparticular hardware resource is maintained. For example, when the thirdapplication service level temporarily does not satisfy the thresholdapplication service level, the adjustment logic 110 provides a fourthallocation 118 of the first hardware resource 122 to support the runningsoftware application 104 upon detection of the non-satisfied applicationservice level. The fourth allocation 118 of the first hardware resource122 is increased from the previous allocation (e.g., the thirdallocation). The fourth allocation 118 may be the same as the secondallocation (e.g., before the most recent allocation reduction). Thus, alast allocation of the first hardware resource 122 that resulted in anapplication service level that satisfied the threshold applicationservice level may be considered an appropriate reduced allocation of thefirst hardware resource 122 to support the software application 104. Thefourth allocation 118 may be assigned to the first hardware resource122. Alternatively, further calculations may be performed using smallerallocation reduction percentages (e.g., reduction seeds 140) to betterpinpoint the appropriate reduced allocation of the first hardwareresource 122 to support the software application 104.

In a particular embodiment, a series of other hardware resourcessupporting the software application 104 (e.g., the second hardwareresource 124 or the third hardware resource 126) are analyzed based onan adjustment order 144. The adjustment order 144 identifies an order inwhich allocations of individual hardware resources are adjusted. Forexample, the adjustment order 144 may identify the second hardwareresource 124 and the third hardware resource 126 as the next hardwareresources to be adjusted.

In a particular embodiment, the adjustment logic 110 provides a firstallocation 118 of the second hardware resource 124 to support therunning software application 104. The measurement logic 112 measureshardware resource metrics 120 associated with the second hardwareresource 124 during an analysis interval. The service level logic 114calculates an application service level based on the hardware resourcemetrics 120 measured during the analysis interval. When the applicationservice level satisfies the threshold application service level, theadjustment logic 110 reduces the allocation 118 of the second hardwareresource 124 until the service level logic 114 calculates an applicationservice level that does not satisfy the threshold application servicelevel. Thus, a last allocation of the second hardware resource 124 thatresulted in an application service level that satisfied the thresholdapplication service level may be considered an appropriate reducedallocation of the second hardware resource 124 to support the softwareapplication 104. In a particular embodiment, the last allocation of thesecond hardware resource 124 that resulted in a satisfactory applicationservice level may be assigned to the second hardware resource 124.Alternatively, further calculations may be performed using smallerallocation reduction percentages (e.g., reduction seeds 140) to betterpinpoint the appropriate reduced allocation of the second hardwareresource 124 to support the software application 104. Similarly, anappropriate reduced allocation of the third hardware resource 126 tosupport the software application 104 may be determined next (e.g., basedon the adjustment order 144).

Referring to FIG. 2, an embodiment of a method that adjusts hardwareresources allocated to support execution of a software applicationduring runtime is illustrated.

The method includes identifying a first hardware resource of one or morehardware resources that support execution of a running softwareapplication, at 202. One or more hardware resources supporting thesoftware application during runtime are identified as targeted forreduced allocation, and the first hardware resource is one of theidentified hardware resources. For example, the first hardware resourcemay include a processor resource (e.g., a CPU), a memory resource, anetwork resource, another physical hardware resource, or a virtualhardware resource (e.g., a cloud computing resource).

At least one hardware resource metric associated with the first hardwareresource is measured during a first analysis interval, at 204. Forexample, the at least one hardware resource metric may include a peakinput/output (I/O) queue length, a peak transaction latency, a peakusage of allocated processing units, a peak usage of allocated memory,or a peak usage of allocated storage space. As another example, the atleast one hardware resource metric may include an average I/O queuelength, an average transaction latency, an average usage of allocatedprocessing units, an average usage of allocated memory, or an averageusage of allocated storage space.

In a particular embodiment, the at least one hardware resource metric isperiodically measured during the first analysis interval, where apolling interval separates each of a plurality of periodic measurements.The polling interval is a time interval between periodic measurements ofthe at least one hardware resource metric. The polling interval betweeneach measurement may be the same amount of time or a different amount oftime. For example, a first hardware resource metric may be measured at afirst time, a second hardware resource metric may be measured at asecond time, and a third hardware resource metric may be measured at athird time. The length of time between the first time and the secondtime may be different from the length of time between the second timeand the third time. As an example, the length of time between the firstmeasurement and the second measurement may be ten minutes, and thelength of time between the second measurement and the third measurementmay be twenty minutes. Alternatively, any other length of time mayseparate measurements of the hardware resource metrics.

A first application service level is calculated based on the at leastone hardware resource metric measured during the first analysisinterval, at 206. The calculated first application service level iscompared to a threshold application service level, at 208. At 210, it isdetermined whether the calculated first application service levelsatisfies the threshold application service level. When the calculatedfirst application service level satisfies the threshold applicationservice level, the method includes reducing a first allocation of thefirst hardware resource to a second allocation of the first hardwareresource, at 212. For example, if the first hardware resource is aprocessor resource, the first allocation may be 80% of the available CPUcapacity. The second allocation of the first hardware resource may be25% lower than the first allocation. Thus, a percentage of CPU capacityavailable to the software application may be reduced from 80% ofavailable CPU capacity to 60% of available CPU capacity. In theparticular embodiment illustrated in FIG. 2, after reducing theallocation of the first hardware resource, the method returns to 204. Byreducing the allocation of the first hardware resource iteratively, theallocation of the first hardware resource is reduced until thecalculated application service level no longer satisfies the thresholdapplication service level.

During the temporary period when the calculated first applicationservice level does not satisfy the threshold application service level,the method includes increasing the allocation of the first hardwareresource upon detection of the non-satisfied application service level,at 214. By increasing the allocation, an adequate allocation of thefirst hardware resource is maintained. The allocation is assigned to thefirst hardware resource, at 216. In a particular embodiment, the lastallocation of the first hardware resource that resulted in a calculatedapplication service level that satisfied the threshold applicationservice level may be considered an appropriate reduced allocation of thefirst hardware resource to support the software application.Alternatively, further calculations may be performed using smallerallocation reduction percentages (e.g., reduction seeds 140 of FIG. 1)to better pinpoint the appropriate reduced allocation of the firsthardware resource to support the software application.

Referring to FIG. 3, another embodiment of a method of adjustinghardware resources allocated to support execution of a softwareapplication during runtime is illustrated.

The method includes identifying a first hardware resource of one or morehardware resources allocated to support execution of a softwareapplication during runtime, at 302. One or more hardware resourcessupporting the software application during runtime are identified astargeted for reduced allocation, and the first hardware resource is oneof the identified hardware resources. For example, the first hardwareresource may include a processor resource (e.g., a CPU), a memoryresource, a network resource, another physical hardware resource, or avirtual hardware resource (e.g., a cloud computing element).

At least one hardware resource metric associated with the first hardwareresource is measured during an analysis interval (e.g., a first analysisinterval), at 304. For example, the at least one hardware resourcemetric may include a peak input/output (I/O) queue length, a peaktransaction latency, a peak usage of allocated processing units, a peakusage of allocated memory, or a peak usage of allocated storage space.As another example, the at least one hardware resource metric mayinclude an average I/O queue length, an average transaction latency, anaverage usage of allocated processing units, an average usage ofallocated memory, or an average usage of allocated storage space.

An application service level (e.g., a first application service level)is calculated based on the at least one hardware resource metricmeasured during the first analysis interval, at 306. The calculatedapplication service level (e.g., a first application service level) iscompared to a threshold application service level, at 308. At 310, it isdetermined whether the calculated application service level satisfiesthe threshold application service level. When the calculated applicationservice level satisfies the threshold application service level, themethod includes reducing an allocation of the first hardware resource,at 312. For example, the allocation of the first hardware resource maybe reduced from a first allocation to a second allocation. For example,if the first hardware resource is a storage device, the first allocationmay be 80% of the storage space available on the storage device. Thesecond allocation of the first hardware resource may be 25% lower thanthe first allocation. Thus, a percentage of storage space available tothe software application may be reduced from 80% of available storagespace to 60% of available storage space.

In the particular embodiment illustrated in FIG. 3, after reducing theallocation of the first hardware resource, the method returns to 304.The at least one hardware resource metric associated with the firsthardware resource is measured during a second analysis interval. Anapplication service level (e.g., a calculated second application servicelevel) is calculated based on the at least one hardware resource metricmeasured during the second analysis interval, at 306. The calculatedapplication service level (e.g., a second application service level) iscompared to the threshold application service level, at 308. At 310, itis determined whether the calculated application service level satisfiesthe threshold application service level. When the calculated applicationservice level satisfies the threshold application service level, themethod includes further reducing the allocation of the first hardwareresource, at 312. For example, the allocation of the first hardwareresource may be reduced from the second allocation to a thirdallocation. Continuing from the previous example, the second allocationmay be reduced from 60% of available storage space to the thirdallocation of 45% of available storage space.

After reducing the allocation of the first hardware resource, the methodreturns to 304. The at least one hardware resource metric associatedwith the first hardware resource is measured during a third analysisinterval. An application service level (e.g., a third applicationservice level) is calculated based on the at least one hardware resourcemetric measured during the third analysis interval, at 306. Thecalculated application service level is compared to the thresholdapplication service level, at 308. At 310, it is determined whether thecalculated application service level satisfies the threshold applicationservice level. When the calculated application service level satisfiesthe threshold application service level, the method includes furtherreducing the allocation of the first hardware resource, at 312. Thus,the method includes reducing the allocation of the first hardwareresource until the calculated application service level no longersatisfies the threshold application service level. When the calculatedservice level no longer satisfies the threshold application servicelevel, the allocation is not an appropriate reduced allocation level tosupport the software application.

In a particular embodiment, when the calculated application servicelevel does not satisfy the threshold application service level, themethod proceeds to 314. At 314, the method includes increasing theallocation of the first hardware resource (e.g., from the thirdallocation to a fourth allocation). In the embodiment shown in FIG. 3,further calculations are performed to better pinpoint the appropriatereduced allocation of the first hardware resource to support thesoftware application. For example, the third allocation of the firsthardware resource (e.g., 45% of available storage space) failed tosatisify the threshold application service level. The second allocationof the first hardware resource (e.g., 60% of available storage space)satisified the threshold application service level. Therefore, theappropriate reduced allocation is between 45% and 60% of availablestorage capacity. In a particular embodiment, at 314, the thirdallocation (e.g., 45% of available storage space) is increased to anallocation that is less than the second allocation (e.g., 60% ofavailable storage space). For example, the third allocation may beincreased by 50% of the difference between the second allocation and thethird allocation, resulting in an increased allocation of 52.5% ofavailable storage capacity.

At least one hardware resource metric associated with the first hardwareresource is measured during an analysis interval of the first hardwareresource, at 316. An application service level is calculated based onthe at least one hardware resource metric measured during the analysisinterval, at 318. The calculated application service level is comparedto the threshold application service level, at 320. At 322, it isdetermined whether the calculated application service level satisfiesthe threshold application service level.

When the calculated application service level does not satisfy thethreshold application service level, the method proceeds to 324. At 324,the method includes increasing the allocation of the first hardwareresource and proceeding to 316 for further measurements and associatedcalculations. In this case, the increased allocation of the firsthardware resource (e.g., 52.5% of available storage space) failed tosatisify the threshold application service level. Therefore, theappropriate reduced allocation is between 52.5% and 60% of availablestorage capacity. As an example, at 324, the allocation of the firsthardware resource may be increased from 52.5% of available storagecapacity to 55% of available storage capacity. The method proceeds to316 for further measurements and calculations. Multiple iterations ofincreasing the allocation of the first hardware resource may be used todetermine an appropriate reduced allocation of the first hardwareresource. When the calculated application service level satisfies thethreshold application service level, the method includes assigning theallocation to the first hardware resource, at 326.

Referring to FIG. 4, another embodiment of a method of adjustinghardware resources allocated to support execution of a softwareapplication during runtime is illustrated.

The method includes identifying a first hardware resource of one or morehardware resources allocated to support execution of a softwareapplication during runtime, at 402. One or more hardware resourcessupporting the software application during runtime are identified astargeted for reduced allocation, and the first hardware resource is oneof the identified hardware resources. For example, the first hardwareresource may include a processor resource (e.g., a CPU), a memoryresource, a network resource, another physical hardware resource, or avirtual hardware resource.

At least one hardware resource metric associated with the first hardwareresource is measured during an analysis interval (e.g., a first analysisinterval), at 404. For example, the at least one hardware resourcemetric may include a peak input/output (I/O) queue length, a peaktransaction latency, a peak usage of allocated processing units, a peakusage of allocated memory, or a peak usage of allocated storage space.As another example, the at least one hardware resource metric mayinclude an average I/O queue length, an average transaction latency, anaverage usage of allocated processing units, an average usage ofallocated memory, or an average usage of allocated storage space.

An application service level (e.g., a first application service level)is calculated based on the at least one hardware resource metricmeasured during the first analysis interval, at 406. The calculatedapplication service level is compared to a threshold application servicelevel, at 408. At 410, it is determined whether the calculatedapplication service level satisfies the threshold application servicelevel. When the calculated application service level satisfies thethreshold application service level, the method includes reducing anallocation of the first hardware resource, at 412. For example, theallocation of the first hardware resource may be reduced from a firstallocation to a second allocation. For example, if the first hardwareresource is a memory resource, the first allocation may be 80% of totalavailable memory. The second allocation of the first hardware resourcemay be 25% lower than the first allocation. Thus, a percentage of memoryavailable to the software application may be reduced from 80% ofavailable memory to 60% of available memory.

As previously described, after reducing the allocation of the firsthardware resource, the method returns to 404. The method includesiteratively reducing the allocation of the first hardware resource untilthe calculated application service level no longer satisfies thethreshold application service level.

During the temporary period when the calculated application servicelevel does not satisfy the threshold application service level, themethod includes increasing the allocation of the first hardware resourceupon detection of the non-satisfied application service level, at 414.By increasing the allocation, an adequate allocation of the firsthardware resource is maintained. The allocation is assigned to the firsthardware resource, at 416. In a particular embodiment, the lastallocation of the first hardware resource that resulted in a calculatedapplication service level that satisfied the threshold applicationservice level may be considered the appropriate reduced allocation ofthe first hardware resource to support the software application.Alternatively, as previously described, further calculations may beperformed to better pinpoint the appropriate reduced allocation of thefirst hardware resource to support the software application.

After assigning the appropriate reduced allocation to the first hardwareresource, the method returns to 402 to identify a second hardwareresource of the one or more hardware resources allocated to supportexecution of the software application during runtime.

At least one hardware resource metric associated with the secondhardware resource is measured during an analysis interval, at 404. Forexample, the at least one hardware resource metric may include a peakinput/output (I/O) queue length, a peak transaction latency, a peakusage of allocated processing units, a peak usage of allocated memory,or a peak usage of allocated storage space. As another example, the atleast one hardware resource metric may include an average I/O queuelength, an average transaction latency, an average usage of allocatedprocessing units, an average usage of allocated memory, or an averageusage of allocated storage space.

An application service level is calculated based on the at least onehardware resource metric measured during the analysis interval, at 406.The calculated application service level is compared to the thresholdapplication service level, at 408. At 410, it is determined whether thecalculated application service level satisfies the threshold applicationservice level. When the calculated application service level satisfiesthe threshold application service level, the method includes reducing anallocation of the second hardware resource, at 412. For example, theallocation of the second hardware resource may be reduced from a firstallocation to a second allocation. For example, if the second hardwareresource is a network resource, the first allocation may be 80% of totalavailable network bandwidth. The second allocation may be 25% lower thanthe first allocation. Thus, a percentage of network bandwidth availableto the software application may be reduced from 80% of total availablenetwork bandwidth to 60% of total available network bandwidth.

As previously described, after reducing the allocation of the secondhardware resource, the method returns to 404. The method includesiteratively reducing the allocation of the second hardware resourceuntil the calculated application service level no longer satisfies thethreshold application service level.

During the temporary period when the calculated application servicelevel does not satisfy the threshold application service level, themethod includes increasing the allocation of the second hardwareresource upon detection of the non-satisfied application service level,at 414. By increasing the allocation, an adequate allocation of thesecond hardware resource is maintained. The allocation is assigned tothe second hardware resource, at 416. In a particular embodiment, thelast allocation of the second hardware resource that resulted in acalculated application service level that satisfied the thresholdapplication service level may be considered the appropriate reducedallocation of the second hardware resource to support the softwareapplication. Alternatively, as previously described, furthercalculations may be performed to better pinpoint the appropriate reducedallocation of the second hardware resource to support the softwareapplication. Further, reduced allocations of other hardware resourcesmay be determined.

It should be appreciated that the appropriate reduced allocation ofother hardware resources to support the software application may also bedetermined. For example, after assigning the appropriate reducedallocation to the second hardware resource, the method may return to 402to identify a third hardware resource of the one or more hardwareresources allocated to support execution of the software applicationduring runtime.

FIG. 5 shows a block diagram of a computing environment 500 including ageneral purpose computer device 510 operable to support embodiments ofcomputer-implemented methods and computer program products according tothe present disclosure. In a basic configuration, the computing device510 may include a computer (e.g., a server) configured to processtransactions such as described with reference to FIG. 1.

The computing device 510 typically includes at least one processing unit520 and system memory 530. Depending on the exact configuration and typeof computing device, the system memory 530 may be volatile (such asrandom access memory or “RAM”), non-volatile (such as read-only memoryor “ROM,” flash memory, and similar memory devices that maintain thedata they store even when power is not provided to them) or somecombination of the two. The system memory 530 typically includes anoperating system 532, one or more application platforms, one or moreapplications 536, and may include program data 538.

The computing device 510 may also have additional features orfunctionality. For example, the computing device 510 may also includeremovable and/or non-removable additional data storage devices such asmagnetic disks, optical disks, tape, and standard-sized or miniatureflash memory cards. Such additional storage is illustrated in FIG. 5 byremovable storage 540 and non-removable storage 550. Computer storagemedia may include volatile and/or non-volatile storage and removableand/or non-removable media implemented in any method or technology forstorage of information such as computer-readable instructions, datastructures, program components or other data. The system memory 530, theremovable storage 540 and the non-removable storage 550 are all examplesof computer storage media. The computer storage media includes, but isnot limited to, RAM, ROM, electrically erasable programmable read-onlymemory (EEPROM), flash memory or other memory technology, compact disks(CD), digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by computing device 510.Any such computer storage media may be part of the device 510. Thecomputing device 510 may also have input device(s) 560 such as akeyboard, mouse, pen, voice input device, touch input device, etc.Output device(s) 570 such as a display, speakers, printer, etc. may alsobe included.

The computing device 510 also contains one or more communicationconnections 580 that allow the computing device 510 to communicate withother computing devices 590, such as one or more client computingsystems or other computers, over a wired or a wireless network. The oneor more communication connections 580 are an example of communicationmedia. By way of example, and not limitation, communication media mayinclude wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, RF, infrared and other wirelessmedia. It will be appreciated, however, that not all of the componentsor devices illustrated in FIG. 5 or otherwise described in the previousparagraphs are necessary to support embodiments as herein described.

The illustrations of the embodiments described herein are intended toprovide a general understanding of the structure of the variousembodiments. The illustrations are not intended to serve as a completedescription of all of the elements and features of apparatus and systemsthat utilize the structures or methods described herein. Many otherembodiments may be apparent to those of skill in the art upon reviewingthe disclosure. Other embodiments may be utilized and derived from thedisclosure, such that structural and logical substitutions and changesmay be made without departing from the scope of the disclosure. Forexample, the one or more hardware resources 106 of FIG. 1 may bephysical resources or virtual resources. Accordingly, the disclosure andthe figures are to be regarded as illustrative rather than restrictive.

Those of skill would further appreciate that the various illustrativelogical blocks, configurations, modules, circuits, and algorithm stepsdescribed in connection with the embodiments disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, configurations,modules, circuits, or steps have been described generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

The steps of a method described in connection with the embodimentsdisclosed herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in computer readable media, such as randomaccess memory (RAM), flash memory, read only memory (ROM), registers,hard disk, a removable disk, a CD-ROM, or any other form of storagemedium known in the art. An exemplary storage medium is coupled to theprocessor such that the processor can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium may be integral to the processor or the processor and the storagemedium may reside as discrete components in a computing device orcomputer system.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any subsequent arrangementdesigned to achieve the same or similar purpose may be substituted forthe specific embodiments shown. This disclosure is intended to cover anyand all subsequent adaptations or variations of various embodiments.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, variousfeatures may be grouped together or described in a single embodiment forthe purpose of streamlining the disclosure. This disclosure is not to beinterpreted as reflecting an intention that the claimed embodimentsrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter may bedirected to less than all of the features of any of the disclosedembodiments.

The previous description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the disclosedembodiments. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedherein may be applied to other embodiments without departing from thescope of the disclosure. Thus, the present disclosure is not intended tobe limited to the embodiments shown herein but is to be accorded thewidest scope possible consistent with the principles and novel featuresas defined by the following claims.

1. A system comprising; adjustment logic to adjust an allocation of afirst hardware resource to support a running software application;measurement logic to measure at least one hardware resource metricassociated with the first hardware resource; wherein the at least onehardware resource metric includes a peak and an average hardwareresource metric; and service level logic to calculate an applicationservice level based on the measured at least one hardware resourcemetric; wherein when the application service level satisfies a thresholdapplication service level, the allocation of the first hardware resourceis iteratively reduced to reach a reduced allocation level where theapplication service level does not satisfy the threshold applicationservice level, and in response thereto, the allocation of the firsthardware resource is increased by an increment, such that theapplication service level again satisfies the threshold applicationservice level; wherein the increment is less than a reduction amountassociated with a previous iterative reduction that resulted in theapplication service level not satisfying the threshold applicationservice level; wherein the at least one hardware resource metric isperiodically measured and wherein a polling interval separates each of aplurality of the periodic measurements.
 2. The system of claim 1,wherein the threshold application service level is a service levelagreement (SLA) threshold.
 3. The system of claim 1, wherein theapplication service level is temporarily reduced below the thresholdapplication service level.
 4. The system of claim 1, wherein theallocation of the first hardware resource is iteratively reducedmultiple times to reach the reduced allocation level where theapplication service level does not satisfy the threshold applicationservice level.
 5. The system of claim 1, wherein the running softwareapplication includes a database application.
 6. The system of claim 1,wherein an allocation of a second hardware resource supporting therunning software application is iteratively reduced until a calculatedapplication service level does not satisfy the threshold applicationservice level, and in response thereto, the allocation of the secondhardware resource is increased such that the application service levelsatisfies the threshold application service level.
 7. The system ofclaim 1, wherein the allocation of the first hardware resource isiteratively reduced by a reduction seed.
 8. The system of claim 1,further comprising one or more software application programminginterfaces (APIs) to interface with the running software application,wherein the one or more software APIs adjust allocation of one or morehardware resources available to the running software application.
 9. Amethod comprising: identifying a first hardware resource of one or morehardware resources, wherein the one or more hardware resources supportexecution of a running software application; measuring at least onehardware resource metric associated with the first hardware resourcewherein the at least one hardware resource includes a peak and anaverage hardware resource metric; calculating an application servicelevel based on the measured at least one hardware resource metricassociated with the first hardware resource; comparing the calculatedapplication service level to a threshold application service level; whenthe calculated application service level satisfies the thresholdapplication service level, iteratively reducing an allocation of thefirst hardware resource until the calculated application service leveldoes not satisfy the threshold application service level and in responsethereto increasing the allocation of the first hardware resource by anincrement such that the calculated application service level againsatisfies the threshold application service level wherein the incrementis less than a reduction amount associated with a previous iterativereduction that resulted in the calculated application service level notsatisfying the threshold application service level; and wherein the atleast one hardware resource metric is periodically measured and whereina polling interval separates each of a plurality of the periodicmeasurements.
 10. The method of claim 9, wherein the allocation of thefirst hardware resource is adjusted using a first applicationprogramming interface (API) associated with the first hardware resource.11. The method of claim 9, further comprising: identifying a secondhardware resource of the one or more hardware resources; measuring atleast one hardware resource metric associated with the second hardwareresource; calculating the application service level further based on themeasured at least one hardware resource metric associated with thesecond hardware resource; when the calculated application service levelsatisfies the threshold application service level, reducing theallocation of the second hardware resource until the calculatedapplication service level does not satisfy the threshold applicationservice level; and when the calculated application service level doesnot satisfy the threshold application service level, increasing theallocation of the second hardware resource such that the calculatedapplication service level satisfies the threshold application servicelevel.
 12. The method of claim 11, wherein the allocation of the secondhardware resource is adjusted using a second application programminginterface (API) associated with the second hardware resource.
 13. Acomputer readable storage medium comprising instructions, that whenexecuted by a processor, cause the processor to: identify a firsthardware resource of one or more hardware resources, wherein the one ormore hardware resources support execution of a running softwareapplication; measure at least one hardware resource metric associatedwith the first hardware resource wherein the at least one hardwareresource metric includes a peak and an average hardware resource metric;calculate an application service level based on the measured at leastone hardware resource metric associated with the first hardwareresource; compare the calculated application service level to athreshold application service level; and when the calculated applicationservice level satisfies the threshold application service level,iteratively reduce the allocation of the first hardware resource untilthe calculated application service level does not satisfy the thresholdapplication service level, and upon detecting that the calculatedapplication service level does not satisfy the threshold applicationservice level, automatically increase the allocation of the firsthardware resource by an increment such that the calculated applicationservice level satisfies the threshold application service level whereinthe increment is less than a reduction amount associated with a previousiterative reduction that resulted in the calculated application servicelevel not satisfying the threshold application service level; andwherein the at least one hardware resource metric is periodicallymeasured and wherein a polling interval separates each of a plurality ofthe periodic measurements.
 14. The computer readable storage medium ofclaim 13, further comprising instructions, that when executed by theprocessor, cause the processor to: identify a second hardware resourceof the one or more hardware resources; measure at least one hardwareresource metric associated with the second hardware resource; andcalculate the application service level further based on the measured atleast one hardware resource metric associated with the second hardwareresource.
 15. The computer readable storage medium of claim 13, whereinthe one or more hardware resources include one or more of a processorresource and a memory resource.
 16. The computer readable storage mediumof claim 13, wherein the at least one hardware resource metric includesat least one of a peak input/output queue length, a peak transactionlatency, a peak amount of usage of processing units, a peak amount ofallocated memory, and a peak amount of usage of storage space.
 17. Thecomputer readable storage medium of claim 13, wherein the at least onehardware resource metric includes at least one of an averageinput/output queue length, an average transaction latency, an averageamount of usage of processing units, an average amount of allocatedmemory, and an average amount of usage of storage space.